Check the below

SET UP --------- 1. The product family item should have forecast control = Consume in the Organization Item Attributes - INV/Organization Items - query the item - select the MPS/MRP Planning tab. 2. The member items should have forecast control = Consume and Derive Additional Pointers: A. The Product Family item must be MPS planned in the Organization Item Attributes (same navigation as above) B. The Member items can be MPS or MRP planned. C. After the forecast is exploded into another forecast or MDS (explosion must be selected or the Members with their respective allocation percentages will not show up), the Product Family item is supposed to show up by design (It will not be picked up by the MPS/MRP planning processes, however, since it's not a true end item but a place holder only). D. Rounding Control can be done so that decimals (caused by the allocation % and forecast quantity) do not show up in the exploded forecast/MDS via the following setup: 1. MPS planned items must have the checkbox enabled for Round Order Quantities in the Organization Item Attributes (same navigation discussed above). 2. MRP Planned Member items must also have Round Order Quantities but a profile setting is also required which is called MRP: Round Source Entries. This profile must be set to Yes. FORECAST CONSUMPTION LOGIC AND CHECKLIST ---------------------------------------- 1. Forecast Consumption Background Information. a. Forecast consumption occurs when a sales order line is demanded but not necessarily booked. b. Forecast consumption does not occur for partial shipments. Partial shipments, however, will consume an active MDS schedule. c. Forecast consumption occurs in a forecast set. Look at the forecasting setup below. The examples below assume that no demand class is used. Forecast Set Set-A Set-B <- both forecast sets have / \ / \ consumption checked / \ / \ Forecasts FC-1 FC-2 FC-3 FC-4 | | | | Part Number 11 11 11 11 | | | | Quantity 100 100 100 100 <- this is the forecasted quantity Example One: If a sales order for 300 is demanded and processed completely, the following will occur: 1) The quantity of forecast FC-1 will be consumed completely. 2) The quantity of forecast FC-2 will be consumed completely. 3) The quantity of 100 will be entered as an over-consumption on the forecast set level for forecast set Set-A. 4) The quantity of forecast FC-3 will be consumed completely. 5) The quantity of forecast FC-4 will be consumed completely. 6) The quantity of 100 will be entered as an over-consumption on the forecast set level for forecast set Set-B. Note: In the example above, Oracle manufacturing treats both forecast sets as independent demand and consumes both sources independently. Example Two: If a sales order for 25 is demanded and processed completely, the planning manager treats both forecast sets independently and the following occurs: 1) A consumption occurs for forecast FC-1, leaving the quantity to be consumed at 75. (Note: While forecast FC-2 also has a quantity to be consumed, the planning manager uses the following logic while consuming the forecast: a) For each forecast set, find all forecasts that have forecast entries for the item. b) Do multiple forecasts have the item as an entry? If not, consume against the forecast and record any over-consumption at the forecast set level. c) If there are multiple forecasts for the item, under the forecast set, sort the forecast names in alphabetical order and consume against the first one chosen until the quantity is completely consumed. Then proceed to the next forecast according to alphabetical order. If all forecasts under the forecast set are completely consumed, record the over-consumption at the forecast set level. 2) A consumption will occur for forecast FC-3, leaving the quantity to be consumed at 75. (Note: While forecast FC-4 also has a quantity to be consumed, the planning manager uses the following logic while consuming the forecast: a) For each forecast set, find all forecasts that have forecast entries for the item. b) Do multiple forecasts have the item as an entry? If not, consume against the forecast and record any over-consumption at the forecast set level. c) If there are multiple forecasts for the item, under the forecast set, sort the forecast names in alphabetical order and consume against the first one chosen until the quantity is completely consumed. Then proceed to the next forecast according to alphabetical order. If all forecasts under the forecast set are completely consumed, record the over-consumption at the forecast set level. 2. Forecast Consumption Checklist. a. Make sure that you can see the sales order demand in the Supply/Demand screen in Inventory. Navigation paths are: Rel.11, 10.7 SC/NCA: Inventory\On-hand,Availability\Item Supply Demand Rel.10.7 Character: NAV\INV\INQUIRY\PLAN\SupplyDemand b. If you cannot see the sales order demand in the inventory supply/demand screen, some investigation into the order needs to be done. c. If you can see the sales order demand here, then a row has been inserted into MTL_DEMAND. Perform the following steps: 1) In MTL_DEMAND check for the status of the UPDATED_FLAG. (See query below for Step 1.) The code meanings for the updated_flag are: 1 - Planning manager has not yet processed this row. Make sure planning manager is running. 2 - Planning manager has touched this row. Proceed to step 2. 2) Check that profile MRP:Compute Sales Order changes is set to yes. (Navigate to System Administrator/Profile/System.) 3) Make sure the following columns are populated in MTL_DEMAND. (See query below for Step 3.) CUSTOMER_ID BILL_TO_SITE_USE_ID SHIP_TO_SITE_USE_ID INVENTORY_ITEM_ID 4) Check your demand class. If you are not using demand classes, proceed to step 5. If you are populating demand classes in order entry, run the query for Step 4 below. If your desired demand class is populated within the rows selected, proceed to step 5. Otherwise, please stop and investigate the missing demand class within OE. 5) Insert a row into mrp_sales_order_updates. (See query below for Step 5). If you have errors in mrp_sales_order_updates, you must address them. Determine the best action to take based upon the error message(s). You may have to log a TAR with support. In any event, the row(s) must be reset for the forecast consumption process to continue. Meanings of process_status: PROCESS_STATUS - Description : Action -------------- ----------- ------ 2-Waiting to be Processed: Make sure planning manager is running. 3-In Process: Rows are being processed by the planning manager. 4-Error: Check ERROR_MESSAGE in the mrp_sales_order_updates table. 5-Successful Completion: Proceed to step 6 below. 6) Check for completed processing by the planning manager. (See query below for Step 6.) In the mtl_demand table, if mrp_date and mrp_quantity are populated and if available_to_mrp is 1, the planning manager has processed this step successfully. Proceed to step 7. Otherwise, investigate why the planning manager did not complete the process. Check the MRP MANAGER log, internal manager log and all planning manager worker logs for clues. 7) Make sure the item in question has the MRP/MPS attribute set to Consume and Derive. 8) Has an entry been made into the forecasting tables for your order and item? (See query below for Step 8.) 9) Additional Questions: a) Have you tried rescheduling one of the orders and see if it is picked by MRP? b) Did you add the demand class to the forecasted item after the order was demanded? 10) Contact Oracle Support. 3. Queries For Each Of The Above Steps. Query for Step 1 above: select updated_flag from mtl_demand where demand_source_header_id = (select sales_order_id from mtl_sales_orders where segment1 = '&your_order'); Query for Step 3 above: select inventory_item_id, customer_id, ship_to_site_use_id, bill_to_site_use_id from mtl_demand where demand_source_header_id = (select sales_order_id from mtl_sales_orders where segment1 = '&your_order'); Query for Step 4 above: select demand_class from mtl_demand where demand_source_header_id = (select sales_order_id from mtl_sales_orders where segment1 = '&your_order'); Query for Step 5 above: select SALES_ORDER_ID, PROCESS_STATUS, substr(ERROR_MESSAGE,1,40) err_msg from mrp_sales_order_updates where sales_order_id in (select demand_id from mtl_demand where demand_source_header_id in (select sales_order_id from mtl_sales_orders where segment1 = '&your_order')); Query for Step 6 above. select substr(b.segment1,1,10) part, substr(demand_source_line,1,10) line_nbr, mrp_date, substr(mrp_quantity,1,5) mrp_q, available_to_mrp available_mrp from mtl_system_items b, mtl_demand a where demand_source_header_id in (select sales_order_id from mtl_sales_orders where segment1 = '&your_order') and b.inventory_item_id = a.inventory_item_id and b.organization_id = a.organization_id; Query for Step 8 above: select a.forecast_designator, a.update_sales_order, c.segment1, b.sales_order_id, a.update_quantity, b.process_status from mtl_system_items c, mrp_forecast_updates a, mrp_sales_order_updates b where b.sales_order_id = (select sales_order_id from mtl_sales_orders where segment1 = '&your_order') and a.update_seq_num = b.update_seq_num and c.organization_id = b.organization_id and c.inventory_item_id = b.inventory_item_id order by 1,2,3;